Systems and methods for prioritized channel access for 802.11ax clients in BSS with mixed clients

ABSTRACT

Systems and methods are described for prioritizing channel access to uplink (UL) multi-user (MU) data capable active stations (STAs) by dynamically adapting a MU enhanced distributed channel access (EDCA) parameter set to provide for increased access to the channel by the UL MU data capable active STAs when the total number of active STAs associated to the AP less the number of active UL MU capable STAs exceeds the number of active UL MU data capable STAs; and by dynamically adapting the MU EDCA parameter set to equal a legacy EDCA parameter set to reduce collisions between the UL MU data capable STAs when the number of active UL MU data capable STAs exceeds or equals the total number of active STAs associated to the AP less the number of active UL MU data capable STAs.

DESCRIPTION OF RELATED ART

In recent years, Wireless Local Area Network (WLAN) technologies haveemerged as a fast-growing market. One example of the various WLANtechnologies is the Institute of Electrical and Electronics Engineers(IEEE) 802.11 standard. Client devices or stations (STAB) within WLANscommunicate with WLAN devices such as access points (APs) to obtainaccess to one or more network resources. APs can refer to digitaldevices that may be communicatively coupled to one or more networks(e.g., Internet, an intranet, etc.). APs may be directly connected tothe one or more networks or connected via a controller. An AP, asreferred to herein, may include a wireless access point (WAP) thatcommunicates wirelessly with devices using Wi-Fi, Bluetooth or relatedstandards and that communicates with a wired network.

APs configure various parameters for communicating with other devices,and for supporting real time services while meeting Quality of Service(QoS) requirements. The specific values configured for variousparameters determine the performance of an access point such as speedand reliability.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure, in accordance with one or more variousembodiments, is described in detail with reference to the followingfigures. The figures are provided for purposes of illustration only andmerely depict typical or example embodiments.

FIG. 1A illustrates an example wireless network deployment in whichchannel access can be dynamically prioritized for Multi User (MU) datacapable WLAN devices (such as 802.11ax WLAN devices) in a Basic ServiceSet (BSS) with mixed clients devices.

FIG. 1B illustrates example values for parameters based on the densityof a type of WLAN device in a BSS with mixed client devices.

FIG. 2A illustrates an example access point (AP) in accordance withvarious embodiments, where channel access is dynamically prioritized forMU data capable WLAN devices (such as 802.11ax STAs) in BSS with mixedclients.

FIG. 2B illustrates an example computing component for effectuatingdynamically prioritized channel access based on the number and/or typesof STAs active on the channel in the AP of FIG. 2A, in accordance withone embodiment.

FIG. 2C illustrates another example computing component for effectuatingdynamically prioritized channel access in the AP of FIG. 2A.

FIG. 2D shows an example method for effectuating dynamically prioritizedchannel access in a BSS in accordance with some embodiments.

FIG. 3 illustrates an example computing component in which variousembodiments described herein may be implemented.

The figures are not exhaustive and do not limit the present disclosureto the precise form disclosed.

DETAILED DESCRIPTION

Multiple client devices (or STAs) in the BSS can transmit frames to anAP with a variety of schemes, which among other benefits, such asincreasing the information throughput on the channel, are employed toreduce the probability of frame collisions. These schemes can include MUuplink (UL) schemes wherein the channel is accessed simultaneously (i.e.at or around the same time, such as by full or partial bandwidthMulti-User Multiple Input Multiple Output (MU-MIMO), MU-OrthogonalFrequency Division Multiple Access (OFDMA), or a hybrid combinationthereof). The channel can also be accessed by other schemes whereinclient devices sense the channel and wait a selected amount of timebefore initiating a transmission (generally single user (SU) schemes).Thus WLAN devices in the BSS can access the channel with MU (generallyMU capable, or high efficiency WLAN devices), but also SU means. Thevariety of WLAN devices and schemes means that the BSS is increasingly amixed client environment. Moreover, with the number of WLAN devicesincreasing as demand for connectivity increases, the risk of framecollisions is also ever increasing. One or more parameters that can beconfigured by an AP can allow for managing channel access with channelaccess priority in mind, while also minimizing the risk of framecollisions.

Although various systems and methods have moved towards addressing theseproblems with new MU schemes and setting fixed values for theseparameters, for the sake or reducing collisions, channel access fromsome client devices can be left unprioritized (or some client devicescan remain handicapped in terms of access to the channel), or whenprioritized, the collision risk may still be too great. Therefore, inaccordance with various embodiments, the present disclosure allows foran intelligent means of dynamically adjusting these parameters based onthe needs of the WLAN devices, but also the BSS as a whole.

Accordingly, disclosed are methods and systems for dynamicallyconfiguring channel access priority. Moreover, disclosed are methods andsystem for prioritizing channel access on uplink for UL MU data capabledevices (such as 802.11ax client devices) over legacy, or non-UL MU datacapable devices, even if these devices choose to also employ SU means ofchannel access. These systems and methods can include dynamicallymodifying one or more of these parameters. Methods and systems disclosedherein can also include dynamically adjusting these parameters based onthe number of active MU capable client devices, and/or the total numberof active client devices in the BSS. In this way, the dynamic system andmethods allow for the balance between competing needs to be preserved,such as priority and speed of WLAN device(s) and the requirements of theBSS.

Before describing embodiments of the disclosed systems and methods indetail, it is useful to describe an example network installation withwhich these systems and methods might be implemented in variousapplications. FIG. 1A illustrates one example of a network configuration100 that may be implemented for an organization, such as a business,educational institution, governmental entity, healthcare facility orother organization. This diagram illustrates an example of aconfiguration implemented with an organization having multiple users (orat least multiple client devices (STAB) 110) and possibly multiplephysical or geographical sites 102, 132, 142. Sites 102, 132, 142 asshown can each correspond to one or more BSS. For example, site 102 caninclude BSS 111 b. BSS 111 b can include and can be serviced by AP 106b. BSS 11 b can include client device 110 a-c. The network configuration100 may include a primary site 102 in communication with a network 120.The network configuration 100 may also include one or more remote sites132, 142, that are in communication with the network 120.

The primary site 102 may include a primary network, which can be, forexample, an office network, home network or other network installation.The primary site 102 network may be a private network, such as a networkthat may include security and access controls to restrict access toauthorized users of the private network. Authorized users may include,for example, employees of a company at primary site 102, residents of ahouse, customers at a business, and so on.

In the illustrated example, the primary site 102 includes a controller104 in communication with the network 120. The controller 104 mayprovide communication with the network 120 for the primary site 102,though it may not be the only point of communication with the network120 for the primary site 102. A single controller 104 is illustrated,though the primary site may include multiple controllers and/or multiplecommunication points with network 120. In some embodiments, thecontroller 104 communicates with the network 120 through a router (notillustrated). In other embodiments, the controller 104 provides routerfunctionality to the devices in the primary site 102.

A controller 104 may be operable to configure and manage networkdevices, such as at the primary site 102, and may also manage networkdevices at the remote sites 132, 134. The controller 104 may be operableto configure and/or manage switches, routers, access points, and/orclient devices connected to a network. The controller 104 may itself be,or provide the functionality of, an access point.

The controller 104 may be in communication with one or more switches 108and/or wireless Access Points (APs) 106 a-c. Switches 108 and wirelessAPs 106 a-c provide network connectivity to various client devices/STAs110 a-j. Using a connection to a switch 108 or AP 106 a-c, a clientdevice/STA 110 a-j may access network resources, including other deviceson the (primary site 102) network and the network 120.

As used herein, a client device (STA) refers to a device including aprocessor, memory, and I/O interfaces for wired and/or wirelesscommunication. Examples of client devices may include: desktopcomputers, laptop computers, servers, web servers, authenticationservers, authentication-authorization-accounting (AAA) servers, DomainName System (DNS) servers, Dynamic Host Configuration Protocol (DHCP)servers, Internet Protocol (IP) servers, Virtual Private Network (VPN)servers, network policy servers, mainframes, tablet computers,e-readers, netbook computers, televisions and similar monitors (e.g.,smart TVs), content receivers, set-top boxes, personal digitalassistants (PDAs), mobile phones, smart phones, smart terminals, dumbterminals, virtual terminals, video game consoles, virtual assistants,Internet of Things (IOT) devices, and the like.

The BSS is in effect WLAN subset or cell, which can include one or moreWLAN devices, such as one or more client devices (STAB), and/or one ormore APs. Individual WLAN devices can become associated with aparticular BSS. Thus WLAN devices (such as client devices) can beassociated with an AP of the BSS. Multiple client devices may beattempting to receive and/or transmit frames in or around the same time,in a multi-user (MU) environment. For example BSS 111 b can be a MUenvironment, and client devices 110 a-110 c can be attempting to receiveand/or transmit frames in or around the same time.

Client devices can access one or more transmission channels (e.g. byradio) by transmitting and/or receiving frames according to one or morestandard or non-standard protocol. The standard protocol may beconfigured for MU use cases. For example, the standard protocol mayallow for sequential transmission so as to avoid frame collisions. Forexample, a WLAN protocol can provide for QoS priority, and/or collisionavoidance. For example, the 802.11 standard allows for channel access byclient devices according to collision avoidance (CSMA/CA) approach. TheCSMA/CA approach includes access-category specific, STA EnhancedDistributed Channel Access (EDCA) parameters which will be discussedbelow. The CSMA/CA approach can generally be referred to as a singleuser (SU) approach, because the goal is to cause transmission of framesat different times. If the channel is accessed simultaneously under thatapproach, this can generally lead to frame collision.

As another example, the 802.11ax standard allows for client devices toaccess the channel simultaneously (i.e. at or around the same time,without collisions). Thus, this can be referred to a MU and/or highefficiency approach. Devices employing such schemes can be referred toas MU data capable WLAN devices or high efficiency WLAN devices (or802.11ax aware with reference to one example standard). This MU methodof channel access by client devices in the UL can be based on receipt ofa trigger frame which generally schedules the client device to transmitin the UL. This is generally called a scheduled based, and/or triggerbased UL MU transmission, however it is not necessary for thistransmission to be preceded by a trigger. The trigger based UL MUtransmission from the WLAN device can be completed immediately uponreceipt of the trigger (e.g. after sensing the channel, or after a shortinter-frame space (SIFS)). Generally, as described herein, these clientdevices can be scheduled client devices, 802.11ax client devices, highefficiency client devices, and/or MU capable client devices. These MUcapable client devices can also access the channel according to acollision avoidance or SU scheme. For example, client devices can electto access the channel by the collision avoidance approach (e.g. by EDCAcontention) and effectively “double dip” for access to the channel byalso attempting to access the channel by MU means (e.g. after receipt ofa trigger frame).

Within the primary site 102, a switch 108 is included as one example ofa point of access to the network established in primary site 102 forwired client devices/STA 110 i-j. client devices 110 i-j may connect tothe switch 108 and through the switch 108, may be able to access otherdevices within the network configuration 100. client devices 110 i-j mayalso be able to access the network 120, through the switch 108. Theclient devices 110 i-j may communicate with the switch 108 over a wired112 connection. In the illustrated example, the switch 108 communicateswith the controller 104 over a wired 112 connection, though thisconnection may also be wireless.

Wireless APs 106 a-c are included as another example of a point ofaccess to the network established in primary site 102 for client devices110 a-h. Each of APs 106 a-c may be a combination of hardware, software,and/or firmware that is configured to provide wireless networkconnectivity to wireless client devices 110 a-h. In the illustratedexample, APs 106 a-c can be managed and configured by the controller104. APs 106 a-c communicate with the controller 104 and the networkover connections 112, which may be either wired or wireless interfaces.Although the controller 104 is picture separately from APs 106 a-c, theAPs 106 a-c can include one or more controller 104 functionality. Thedivision of the functionality can depend on the MAC mode. For example,in some embodiments (e.g. for local MAC mode), the controller 104functionality is part of the APs106 a-c and/or the controller 104. Insome embodiments (e.g. for split MAC mode) the controller 104functionality can be split among the controller 104 and one or more ofthe APs.

Wireless APs can support UL and/or DL of frames according to one or moreprotocol. For example, the 802.11 standard allows for channel accessaccording to the CSMA/CA approach (e.g. with access-category specificEDCA parameters which will be discussed below), as will be discussedbelow and as previously mentioned, does not allow for client devices totransmit simultaneously (i.e. at or around the same time), thus it canbe referred to as single user (SU) approach.

As another example, the 802.11ax standard allows for channel access byWLAN devices, by a means in addition to the traditional CSMA/CAapproach. The additional means can allow for multiple client devices toaccess the channel simultaneously (i.e. at or around the same time).This approach can be enabled by central scheduling (e.g. by AP, such asAP106 a-c). This approach can be based on the AP accessing the medium(e.g. by using the traditional CSMA/CA approach) and transmitting (i.e.in the DL) a trigger frame to specific client devices. The trigger framecan schedule certain clients to transmit in the UL simultaneously (i.e.at or around the same time). A trigger frame can be used generally forOFDMA, MU-MIMO, and/or Trigger-based Random Access. The trigger framecan contain scheduling information (e.g. resource unit (RU) allocations)for client devices, and/or modulation and coding scheme (MCS) that canbe used for each of the client devices.

For example, for OFDMA, each client device can be allocated one or moreRUs (e.g. subcarrier bandwidths), and thus multiple client devices in anMU environment can transmit simultaneously (e.g. at or around the sametime).

For another example, for UL MU-MIMO, an AP may simultaneously (i.e. inor around the same time) receive from multiple client devices. WhereasOFDMA separates receivers to different time-frequency RUs, with MU-MIMOthe devices are separated to different spatial streams. In 802.11ax,MU-MIMO and OFDMA technologies can be used simultaneously. To enable ULMU transmissions, the AP transmits the trigger frame which containsscheduling information (e.g., for the various MU schemes). Furthermore,the trigger frame also provides synchronization for an uplinktransmission, since the transmission (i.e. from the STA) starts afterSIFS at the end of the trigger frame.

Consequently, a BSS can have a mixed population of UL MU data capableclient devices (e.g. 802.11ax aware client devices or high efficiencyclient devices) and legacy, non UL MU data capable (i.e. non 802.11axaware) client devices. In addition, UL MU data capable WLAN devices canchoose to forgo UL MU transmissions (and thus chose to transmit by SUmeans, e.g. CSMA/CA). In such BSS with mixed client device populations,there can be one or three types of transmissions in the UL:

a. MU from UL MU data capable client devices (e.g. trigger based for802.11ax MU-MIMO and OFDMA);

b. SU (e.g. CSMA/CA (e.g. with EDCA parameters)) by UL MU data capableclient devices (such as 802.11ax aware client devices);

c. SU (e.g. CSMA/CA (e.g. with EDCA parameters)) by non UL MU datacapable client devices (e.g. non 802.11ax aware client devices).

It can be useful for the AP to manage traffic flow and/or channel accessso as to minimize frame collisions in the mixed client population, butalso to respect WLAN device requested and/or enterprise requestedpriority (such as channel access priority).

As used herein, active WLAN devices are referred to as active WLANdevices that are actually transmitting (or attempt to transmit), ascontrasted with dormant WLAN devices which can be associated with an AP,but not transmitting (or not attempting to transmit). As used herein,active client devices are client devices that have one or more frames ordata in a buffer/transmission queue to be transmitted, for the channel.

As used herein, HE-clients can refer to active high-efficiency clientdevices that can support UL MU for data frames (and/or do actually useor attempt to use UL MU for data frames). HE-client-density can refer tothe ratio of active HE-clients over the total number of active clientsin the BSS (i.e. UL MU data capable and non UL MU data capable.) IfHE-clients refer to active high efficiency client devices that cansupport UL MU for data frames and do attempt to use UL MU for dataframes, the rest of the client devices that are not HE-clients caninclude all legacy client devices (e.g. non UL MU data capable clientdevices), and the UL MU data capable (e.g. 802.11ax aware) clientdevices that disable (or chose not to employ) UL MU for data frames.

The network 120 may be a public or private network, such as theInternet, or other communication network to allow connectivity among thevarious sites 102, 130 to 142 as well as access to servers 160 a-b. Thenetwork 120 may include third-party telecommunication lines, such asphone lines, broadcast coaxial cable, fiber optic cables, satellitecommunications, cellular communications, and the like. The network 120may include any number of intermediate network devices, such asswitches, routers, gateways, servers, and/or controllers, which are notdirectly part of the network configuration 100 but that facilitatecommunication between the various parts of the network configuration100, and between the network configuration 100 and othernetwork-connected entities.

An AP generally refers to a networking device that allows a clientdevice or STA to connect to a wired or wireless network, in this case,wireless network 100. An AP can include a processor, memory, and I/Ointerfaces, including wired network interfaces such as IEEE 802.3Ethernet interfaces, as well as wireless network interfaces such as IEEE802.11 WiFi interfaces, although examples of the disclosure are notlimited to such interfaces. An AP can include memory, includingread-write memory, and a hierarchy of persistent memory such as ROM,EPROM, and Flash memory. Moreover, as used herein, an AP may refer toreceiving points for any known or convenient wireless access technologywhich may later become known. Specifically, the term AP is not intendedto be limited to IEEE 802.11-based APs.

It should be noted that APs, such as AP 130, AP 132, and AP 134 areenabled to implement VAPs, namely, support for one or more multipledistinct SSID values over a single AP radio with unique media accesscontrol (MAC) addresses per SSID (i.e., BSSID). As is known, an SSID isa field between 0 and 32 octets that may be included as an InformationElement (IE) within management frames. In the context of the 802.11standard, management frames supporting the SSID IE include the beacon,probe request/response, and association/reassociation request frames. Inone embodiment, an AP supports VAPs using multiple BSSIDs. Each beaconor probe response may contain a single SSID IE. The AP sends beacons foreach VAP that it supports at a beacon interval (e.g., 100 ms), using aunique BSSID for each VAP. The AP responds to probe requests forsupported SSIDs (including a request for the broadcast SSID) with aprobe response including the capabilities corresponding to each BSSID.In one embodiment, an AP may advertise up to a given number (e.g., 16)of beacons, each with a different BSSID to provide the VAP support. EachVAP may have a unique MAC address, and each beacon may have a networkname.

APs as discussed herein can determine if client devices are MU datacapable client devices (e.g. 802.11ax aware) and/or high efficiencydevices. For example, 802.11ax client devices may be UL MU capabledevices, and may choose to disable UL MU. AP's as discussed herein candetermine which MU data capable client devices chose not to employ MUdata schemes, (i.e. employ SU schemes and/or disable MU). APs asdiscussed herein can determine the number of client devices associatedto the AP which are MU data capable, UL MU capable, and/or chose toemploy (or not) MU schemes. AAPs as discussed herein can determine ifclient devices are not MU data capable (i.e. not 802.11ax aware, nonhe-devices, or legacy client devices). APs as discussed herein candetermine the number of client devices associated to the AP which arenot MU data capable. APs as discussed herein can determine the totalnumber of client devices associated to the AP (and/or the BSS size).

It should be understood that wireless communications as contemplatedherein may involve the configuration of one or more parameters whichdetermine a QoS for communication by or with WLAN devices, such as,e.g., APs. Parameter values determine how frequently WLAN devicesrequest access to a radio frequency channel and/or use a radio frequencychannel. Parameter values for a particular WLAN device that result in aradio frequency channel (or an overlapping portion of two radiofrequency channels) being accessed more often by that particular WLANdevice relative to other WLAN devices may be referred to herein asaggressive parameter values. In addition, parameter values that are moreaggressive relative to default or industry-standard parameter values forobtaining channel access may also be referred to herein as aggressiveparameter values. Parameter values for a WLAN device that result in achannel being accessed less often for that particular device, may bereferred to as less aggressive, or a conservative parameter values.Examples of parameters are Enhanced Distributed Channel Access (EDCA)parameters (or legacy EDCA parameters), MU EDCA parameters (EDCAparameters that can be tailored for MU capable WLAN devices), and HybridCoordination Function Controlled Channel Access (HCCA) parameters.

EDCA Parameters

Values for at least some EDCA parameters may depend on values for one ormore other EDCA parameters. Values for EDCA parameters may depend onwhich WLAN device accesses the medium (e.g. client devices, or the AP),and/or the direction (UL or DL). EDCA parameters may include, but arenot limited to the following:

a. Access Category (AC)—An access category parameter refers to one of avoice AC, a video AC, a best effort AC, and a background AC. There maybe more ACs as described in the 802.11 standard and each AC may beassociated with a different QoS priority level.

b. Arbitration Inter-Frame Spacing (AIFS)—A non-random time intervalbefore starting random backoff, which can depend on the AC. It is amethod of prioritizing one AC over the other. In some standards, thiscan correlate to a time interval between frames.

c. Minimum Contention Window (CWmin)—Input to an algorithm thatdetermines the initial random backoff wait time for retry of atransmission in response to failed attempt (for example, due tounavailability of a radio frequency channel). Such an algorithm may beincluded as part of collision avoidance schemes such as CSMA/CA. Forexample, the WLAN device can sense the channel, and then backoff andwait for the random back off wait time before attempting a transmission.The contention window can refer to a range of possible values from whicha random value for the random backoff wait time can be selected.Generally, a smaller contention window can be more aggressive (thusfavor prioritized WLAN device channel access priority). A largercontention window is generally less aggressive (more conservative),which can generally allow for lower probability of collisions. Thecontention window can have a minimum and a maximum value. The minimumvalue is typically the initial value. The contention window can increasewith each successive collision and/or channel access attempt. Themaximum contention window is typically the maximum contention windowsize, (i.e. the contention window size before attempts are aborted).

In binary exponential random backoff algorithms, the contention windowcan be calculated by the equation CW=2{circumflex over ( )}N−1. Thecontention window may depend on the access category, and/or if there hasbeen a prior collision during a prior transmission attempt. In someembodiments, for example, for WLAN devices with traffic in the BestEffort or Background Access Categories, the starting value of N can be4. Thus, in these examples where the starting value of N is 4, CWmin=15.As previously discussed, the random backoff wait time may be increasedwhen a frame transmission is unsuccessful due to the channel beingunavailable for the transmission.

Generally, a lower value for CWmin may be more aggressive than a highervalue for CWmin. A higher value for CWmin may be more conservative thana lower value for CWmin.

d. Maximum Contention Window (CWmax)—can correspond to the maximumrandom backoff wait time. As previously discussed, the random backoffwait time may be increased when a frame transmission is unsuccessful. Ina binary exponential random backoff algorithm, the contention window canbe calculated by the equation CW=2{circumflex over ( )}N−1. In somenon-limiting embodiments, client devices (such as 802.11 client devices)can attempt to re-transmit data up to 7 times before giving up anddropping the frame. In the 802.11 standard, with each collision(unsuccessful attempt of transmission), the value of N is incrementeduntil a successful transmission occurs. Thus N can increase by 1 witheach subsequent attempt and be reset (e.g. to CWmin) when a successfultransmission occurs.

In one non-limiting example where N=4 (e.g. for WLAN devices using theBest Effort or Background QoS Access Categories, CWmin can be 15 (N=4)and CWmax can be 1023 (N=10). This example is reflected in the tablebelow.

TABLE 1 Attempt Contention # N Value Window (2^(N)-1) 1 4 0-15  2 50-31  3 6 0-63  4 7 0-127 5 8 0-255 6 9 0-511 7 10  0-1023 8 10 or NA0-1023 or Give Up. (Dropped Frame)

Generally, a lower value for CWmax may be more aggressive than a highervalue for CWmax. A higher value for CWmax may be more conservative thana lower value for CWmax.

e. Maximum Burst—The maximum burst length allowed for packet bursts(collection of multiple frames transmitted without header information)on the wireless network.

f. Transmission Opportunity (TXOP) Limit—An interval of time when aclient device has the right to initiate transmissions toward an AccessPoint and send as many frames as possible.

g. Beacon Interval—An interval of time between beacon frametransmissions. A beacon frame is one of the management frames in IEEE802.11 based WLANs and includes information about the network. A beaconframe broadcasted by an access point may include values for parametersassociated with that access point.

h. DTIM Period—A number that determines how often a beacon frameincludes a DTIM. A value of the DTIM is included in each beacon frame. ADTIM is included in beacon frames to indicate to the client deviceswhether the access point has buffered broadcast and/or multicast datawaiting for the client devices.

i. User Priorities (UP)—Another QoS related parameter that can map toAC.

MU EDCA Parameters

MU EDCA parameters can include one or more of the legacy EDCA parametersmentioned above, but not necessarily configured to the same valuesthereof. Values for the MU EDCA parameters can be tailored to MU channelaccess schemes. The values for one of the MU EDCA parameter may dependon values for another (i.e. another type) of the MU EDCA parameters. Forexample, the values for MU EDCA contention window, e.g. CWmin, maydepend on the value for MU EDCA AC. The values for the MU EDCAparameters may depend on which WLAN device is accessing the channel(e.g. AP, client devices), and/or the direction (DL or UL).

One or more legacy EDCA parameters, if included in the MU EDCAparameters, can have values set to different, MU scheme (e.g. ODFMA,MU-MIMO) tailored values. One or more standard, such as the 802.11axstandard, provides separate MU EDCA parameter set that can betemporarily used by MU capable client devices (such as 802.11ax awareclient devices) after they have scheduled UL. For example, the MU EDCAparameters may be included as part of the trigger frame that can bereceived from the AP by the client device. As another example, receiptof the trigger frame or another scheduling frame, can trigger the switchto MU EDCA parameters.

In embodiments, the MU EDCA parameters are used by MU data capabledevices that attempt to access the channel by SU means (e.g CSMA/CAapproach with MU EDCA parameters instead of the legacy EDCA parameters).Such MU data capable devices may have received a trigger frame, orotherwise received scheduling information for MU transmission. Such MUdata capable devices may attempt to access the channel by both MU means(e.g. based on the trigger frame or otherwise based on schedulinginformation), and attempt to access the channel by SU means (e.g. byCSMA/CA approach using the MU EDCA parameters). These MU data capableWLAN devices may end up accessing the channel by the means which is morefavorable to the WLAN device. For example, if the random backoff waittime is longer than the otherwise scheduled or trigger basedtransmission time by MU means, the WLAN device could elect to access thechannel by MU means. As another example, if the random backoff wait timeis shorter than the otherwise scheduled or trigger based transmissiontime by MU means, the WLAN device could elect to access the channel bySU means.

The MU EDCA Parameter set can include a MU EDCA timer. A value for theMU EDCA timer can determine the duration after a scheduled ULtransmission for which the MU EDCA parameter set (or portion thereof)take effect. Once MU EDCA timer expires, the WLAN device can revert backto the EDCA parameter set (i.e. legacy EDCA parameters), or otherwiseconfigure the MU EDCA parameter set to have the same values as thelegacy EDCA parameter set.

MU EDCA parameters, such as MU EDCA timer, can be programmed by the AP(or another scheduler WLAN device), or the controller 104. Inembodiments, MU EDCA parameters can be dynamically selected, modified,or adjusted.

For example, the value for the MU EDCA timer can be dynamicallyadjusted. The value for the MU EDCA timer can be based on the values ofother MU EDCA parameters, the values of EDCA parameters, the number ofclient devices associated to the AP, the number of active client devicesassociated to the AP, the number of client devices part of the BSS, thenumber of active client devices part of the BSS, the type of MUtransmission (e.g. OFDMA, MU-MIMO etc.) the number of HE-clients, the RUsize, the number of available RUs, the transmission direction (e.g. DLor UL), the average air-time for each UL and/or MU transmission, thequeue-depth (i.e. for data at one or more buffer(s) of client devicesand/or for a transmission queue, e.g. measured in bytes), the number ofbuffers queued, and/or the UL and/or DL time. In embodiments, the valuefor the MU EDCA timer can be determined by the amount of data bufferedat the he-clients, and/or the number of he-clients (i.e. in the BSSand/or associated to the same AP). For example, if the BSS has N clientdevices that are scheduled at a time (on average or absolute) and eachof the UL schedules takes an air-time of t (e.g. on an average), thenthe value for the MU EDCA timer, T, can be such that it is greater thanor equal to N*t/n. The air time (e.g., UL air time), t, in turn, can bebased one on the number of buffers queued at the WLAN devices (e.g. atthe client devices for UL) and the data-rate programmed for thetransmissions.

In other words, a lower bound on the value for the MU EDCA timer can bedetermined such that the AP can schedule each of the HE-clients at leastonce before the MU EDCA timer expires. If the MU EDCA timer value ishigher than that (i.e. longer than the time it takes to schedule each ofthe he-clients at least once, or higher than the lower bound), thiswould allow the he-clients to have MU EDCA-based SU access to thechannel for a longer duration.

In some embodiments, the value for the MU EDCA timer can be determinedbased on the amount of data buffered at the active high efficiencyclient devices and the number of high efficiency client devices, suchthat each of the high efficiency client devices can be scheduled oncebefore the expiration of the MU EDCA timer.

As previously mentioned, MU capable (e.g. 802.11ax aware) client devicescan elect to access the channel (e.g. in the UL) by traditionalcollision avoidance schemes (such as CSMA/CA approach) and/or to accessthe channel by MU approached (such as MU-MIMO, CFDMA, or generallyscheduled or trigger based approaches). MU EDCA parameters can bespecifically used by these devices which elect to do both (effectivelydouble-dipping on channel access). Thus MU EDCA parameters can be usedfor SU access by WLAN devices which specifically elect to use SU meanseven though they are MU capable.

As previously mentioned, in embodiments, values for MU EDCA can bedynamically adjusted and/or modified. The value for the MU EDCAparameters can be based on the values of other MU EDCA parameters, thevalues of legacy EDCA parameters, the number of client devicesassociated to the AP, the number of active client devices associated tothe AP, the number of client devices part of the BSS, the number ofactive client devices part of the BSS, the type of MU transmission (e.g.OFDMA, MU-MIMO etc.) the number of he-clients, the RU size, the numberof available RUs, the transmission direction (e.g. DL or UL), if therehas been a prior collision (or generally the transmission attemptnumber).

In some embodiments, the values for MU EDCA parameters are the same aslegacy EDCA parameters. For example, values for parameters in the MUEDCA parameter set can be set equal to values for the legacy EDCAparameters when the number of UL MU-capable client devices (e.g.802.11ax capable client devices) exceed the total number of activeclient devices less the number of UL MU-capable client devices. In someembodiments, values for parameters in the MU EDCA parameter set can beset equal to values for the legacy EDCA parameters when the number of ULMU-capable client devices (e.g. 802.11ax capable client devices) areequal to the total number of client devices less the number of ULMU-capable client devices.

In some embodiments, the values for MU EDCA parameters for MU capableclient devices can be more conservative than the values of legacy EDCAparameters. In some embodiments, the values for MU EDCA parameters forMU capable client devices can be more conservative than legacy EDCAparameters, but only for such devices which elect to access the channelby both MU means (e.g. trigger frame based or scheduled based), and SUmeans (such as CSMA/CA approach). Thus, the MU EDCA values can be moreconservative for those client devices which are effectively doubledipping on channel access, than the rest of the client devices, with theaim to reduce collision for legacy EDCA. This can be a fairness policyfor the BSS, and bring fairness between 802.11ax clients that have MUaccess (such as scheduled or trigger based access) as compared to MUcapable (e.g. 802.11ax aware client devices) or non-MU capable clientdevices (e.g. non 802.11ax aware client devices) that do not have MUaccess (i.e. elect to forgo such access or otherwise are not MUcapable).

In some embodiments, values for the MU EDCA parameters are set to bemore aggressive than legacy EDCA parameters. For example, it may bebeneficial to maintain more aggressive than legacy EDCA parameters forbetter performance (or more prioritized channel access) for WLAN deviceswhich access the channel by MU means (e.g. MU capable devices, includingif they elect to “double dip” on channel access by also employingCSMA/CA channel access approaches). In such embodiments, it may bepreferable to not penalize or handicap client devices which do elect toaccess the channel by multiple means. Thus, a dynamic approach toadjusting MU EDCA parameters may consider both BSS requirements, butalso individual client device priority or performance.

In some embodiments, a dynamic approach considers the number of totalactive client devices, but also the number of MU capable WLAN devicesthat can support MU transmissions.

In some embodiments, the MU EDCA parameters can be set to moreconservative, the same as, or more aggressive than legacy EDCAparameters, depending on the Access Categories (or other QoS scheme).For example, for some enterprise critical applications, such as businessvideo, do not have to be handicapped or penalized for “double dipping”,whereas other background applications could be. For example, when the ACis higher priority, such as for video, as compared to lower priority(such as for background), legacy EDCA parameters can be set to moreaggressive.

Values for MU EDCA parameter(s) can be set based on the ratio betweentotal number of active client devices (i.e. the total number of activeclient devices, including UL MU-capable devices such as 802.11ax awareclient devices, and UL MU non-capable devices, such as legacy 802.11devices) and UL MU-capable client devices (such as 802.11ax capableclient devices).

The MU EDCA parameter set can be adjusted based on negotiations betweenthe AP and the client devices, and/or based on a channel access historyfor the client devices. For example, the AP can set to more aggressivethe MU EDCA parameters (such as increase the MU EDCA timer) for a clientdevice which had experienced longer channel access wait times in priorchannel access.

Values for parameters in the MU EDCA parameter set can be based on theratio of active UL MU capable client devices to the total number ofclient devices (i.e. UL MU capable and UL non-capable client devices)associated to an AP. Values for parameters in the MU EDCA parameter setcan be based on the ratio of active UL MU-capable client devices to thetotal number of client devices (i.e. UL MU capable and UL non-capableclient devices) within a BSS. Values for parameters in the MU EDCAparameter set can be based on the total number of WLAN devices and theproportion that can support UL MU for data frames. Values for parametersin the MU EDCA parameter set can be based on the he-client-density.

he-client-density (or another ratio or density described herein) can becompared to a density threshold. If the he-client-density is lower thanthe density threshold, values for the MU EDCA parameters can be moreaggressive than the EDCA parameters. For example, the density thresholdcan be at, below, or around 50%, e.g. 52%, 51%, 50%, 49%, 45%, 40%, 35%,30%, 25%, 10%, 05%, 01%. This can allow for HE-clients to access thechannel more often. Moreover, the MU EDCA timer can be set for longer(thus allowing the WLAN device to have more aggressive parameters forlonger).

In embodiments, values for MU EDCA parameters can be set to be moreaggressive than the EDCA parameters, when the he-client density (oranother ratio or density described here) is at or below a firstthreshold. The values for MU EDCA parameters can be set to be even moreaggressive (i.e. compared to the values when the density is at the firstthreshold) when the he-client density (or another ratio or densitydescribed here) is at or below (i.e. does not exceed) a second densitythreshold value that can be lower than the first density thresholdvalue. In embodiments, It can be understood that there can be one ormore, two or more, three or more, four or more density threshold values.Moreover, the MU EDCA timer can be set for even longer (thus allowingthe WLAN device to have more aggressive parameters for even longer).

FIG. 1B illustrates example values for parameters (e.g. MU EDCAparameters) based on the density of a type of WLAN device in a BSS withmixed client devices. For example, the density can be he-client densityas described herein, and/or the ratio of (active) MU UL data capableWLAN devices associated to the AP, and all the (active) WLAN devicesassociated to the AP. As shown in the graphs 180 a, 180 b, 180 c, 180 d,the values can be set to be more conservative and/or more aggressive (onan aggressiveness scale, which can relate to, for example the access tothe channel). The values can be based on one or more thresholds on thedensity. Although specific threshold values are not shown, it isunderstood that there can be multiple thresholds. Plotting the valuesfor MU EDCA parameters, for example, with respect to the density, it canbe seen that the values for MU EDCA parameters can follow one or morecurves, such as curves 190 a, 190 b, 190 c, 190 d. The curves can followany combination of type of curve (and/or function), for example, step,linear, exponential, non-linear, logarithmic, logistic, etc. It can beunderstood, that the increment to the aggressiveness of the parameterscan be some function of the density. For example, once the density goesbelow and/or at a first threshold, the incremental aggressiveness canfollow a first function (such as a linear function). As another example,the incremental aggressiveness can be flat above that same threshold(thus no increment to the aggressiveness). The examples of FIG. 1B aremerely non-limiting examples.

The lower bound on the MU EDCA parameters can be set by the number ofhe-clients. Making the lower bound on the MU EDCA parameters moreaggressive could cause more frame collisions for the he-clients (e.g.because of a smaller initial contention window). This could bedetrimental to channel utilization by those he-clients, but also byother WLAN devices. For example, if the BSS size (e.g. in terms of thenumber of active client devices, the number of active he-devices, and/orthe number of client devices associated to the AP) is quite small (e.g.1-15 (active) he-clients), then being aggressive with MU EDCA parameterset might more feasible (i.e. in terms of less probability ofcollisions) than with a larger BSS size (e.g. 100-200 activehe-clients). In generally, the probability of collision is lower with alower number of (active) client devices, thus MU EDCA parameters can beset more aggressive. With a larger BSS size, the absolute number ofhe-clients can warrant the MU EDCA parameter set to be less aggressivethan otherwise.

As previously discussed, MU EDCA parameters and/or legacy EDCAparameters can depend on values for QoS related parameters (e.g. ACand/or UP). In embodiments, values for the MU EDCA parameters and/orlegacy EDCA parameters can be set to not be more aggressive (i.e. can beequal to, less aggressive, or more conservative) than values for the MUEDCA parameters (and/or legacy EDCA parameters) for the highest priorityAC or UP. For some of these embodiments, values for the MU EDCAparameters can be more aggressive than the legacy EDCA parameters if thehe-client-density is lower than 50%. In some embodiments, MU EDCAparameters and/or legacy EDCA Parameters can be more aggressive in theDL (e.g. from AP) than in the UL (e.g. from the client device). Forexample, it may be preferable for the AP to set its own aggressiveparameters for transmitting trigger frames. In some examples, the AP canset use the highest priority AC to send the trigger frames (or otherscheduling information).

CWmin MU EDCA parameter can be half or less than half of the CWminlegacy EDCA parameter (e.g. in embodiments with binary exponentialbackoff algorithms). In other words, CWmin legacy EDCA parameter can bedouble or more than double the CWmin MU EDCA parameter. Thus, if thereis one frame collision by MU capable devices employing SU channel accessmeans (i.e. with MU EDCA parameters), the contention window forsubsequent channel access attempts will be smaller (thus moreaggressive), than the initial contention window for SU channel access byWLAN devices employing legacy EDCA parameters (e.g. non MU capableclient devices). In other words, this can allow for more aggressiveparameters for the MU WLAN devices (and thus prioritized channelaccess), even conceding one or more collision.

Moreover, CWMin MU EDCA parameter can be half or less than half of theCWmin legacy EDCA parameter, but only if he-client-density is below acertain density threshold. For example, the density threshold can be 5%,10%, 15%, 20%, 25%, 30%, 40%, 45%, 50%, 51%, 52%. Moreover, CWMin MUEDCA parameter can be half or less than half of the CWmin legacy EDCAparameter, but only if the total number of active clients, or total ofone or some type of clients (e.g. active he-clients), are below acertain threshold.

Similarly, CWmax MU EDCA parameter can be half or less than half of theCWmax EDCA parameter. Similarly, CWmin MU EDCA parameter can be onefourth or less than one fourth of the CWmax legacy EDCA parameter. Thiscould allow for concession or two or more collisions, yet stillmaintaining aggressiveness for MU EDCA parameters (compared to legacyEDCA parameters).

In some of these embodiments, values for the MU EDCA parameters can bemore aggressive than the legacy EDCA parameters if the he-client-densityis lower than 50%. For example, if he-clients experience a collisionbetween transmitted frames, and the contention window is doubled (i.e.for the subsequent transmissions), the aggressiveness can still remainbetter or at par with the aggressiveness of the larger client-base inthe BSS, and not any worse. In other words, just one collision for oneof the he-clients should not make its channel-access capability worsethan that of the legacy (i.e. non MU data capable) client devices.

In embodiments, he-client-density can be equal to or greater than 50%.In this case, the number of he-clients can be equal to or greater thanthe number of non he-clients (i.e. non MU capable client devices). Inthese cases, values for parameters in the MU EDCA Parameter set can beset as the same as values for parameters in the legacy EDCA parameterset. This can ensure that while the he-clients get better channel-access(e.g. due to MU, scheduled and/or trigger based frame transmission inthe UL), frame from these he-clients do not engage in more collisionsdue to aggressive channel access. Collisions may increase the MUcontention window for the some of the he-clients to a point where theaggressiveness (or probability of channel access) may be worse (i.e.less aggressive) than the aggressiveness of legacy EDCA parameters fornon MU capable client devices (e.g. non he-clients). In other words, ifthere is a collision of a frame for he-clients, the subsequentcontention window can increase and become larger than the contentionwindow for non MU capable client devices (i.e. non he-clients). Settingvalues for parameters in the MU EDCA Parameter set as the same as valuesfor parameters in the legacy EDCA parameter set when thehe-client-density is 50% or more, can prevent the favoring towards nonMU-capable client devices, as compared to MU capable client devices thathave experienced a prior collision for a frame.

In embodiments, when the he-client-density is 50% or more, values forparameters in the legacy EDCA parameter set can be more conservative,and values for parameters in the MU EDCA parameter set can be set thesame as the values for parameters in the legacy EDCA parameter set; orvalues for parameters in the MU EDCA parameter set can be set the sameas the values for parameters in the traditional legacy EDCA parameterset (the ones before making the parameter set conservative.

The WLAN protocol operates on channel access using collision avoidance(CSMA/CA) mechanism where any entity in the BSS can access the mediumonly after sensing the channel for a randomly chosen amount of time(random back-off) before initiating a transmission. The range of thisrandomly chosen time is determined by the legacy EDCA parametersprogrammed on the WLAN capable device. The legacy EDCA parameters arespecific to an access-category and are advertised by the AP in a BSS.The client devices can be required to use them for their randomback-off. In order for AP to have better access to the medium, thestandard allows for the AP to use a separate set of AP-EDCA parametersthat are in general more aggressive (more probability of gaining channelaccess) than the STA-EDCA parameters that it advertises. The AP-EDCAparameters are generally more aggressive than the STA-EDCA parameters soas to allow the AP to exert better access to the channel.

EDCA allows for prioritizing contention-based wireless medium (WM)access by classifying 802.11 traffic types by User Priorities (UP)and/or Access Categories (AC). EDCA is used by stations that support QoSin a QoS BSS to provide prioritized WM access. Similarly, two or moreclient devices can compete for access to the shared radio frequencychannel. 802.11 Medium Access Control implemented with the DistributedCo-ordination Function (DCF) and Enhanced DCF Channel Access (EDCA)method can use a random back-off counter to help ensure that clientdevices do not transmit their data at the same time, but rather taketurns to send their data one after the other. This can allow forcollision avoidance in the UL.

When two (or more) 802.11 client devices both have data to send on thesame channel and both have established that the channel is clear, bothstations will select a random number, wait a pre-defined period called aDCF Interframe Space (DIFS) and then start counting from the randomnumber to zero. The first station to reach zero transmits its frame. Theother client devices can return to idle state until the firsttransmission is completed. Once the transmission is over and it is timefor the second station to contend for the channel medium again, it willgo through the process again and simply start counting down from whereit left off. The first station, if it has more data to transmit, willselect another random number and contend for the channel medium again.

If two (or more) 802.11 client devices select the same random numbers,this can lead to traffic collision. According to 802.11, for WLANchannel access, the 802.11 client devices would have to select newrandom numbers and rejoin the queue, however in order to try and reducethe probability of a future collision, the range of random numbers (thecontention window) which can be selected increases, e.g. doubles. Thus,with each consecutive collision, the range of random numbers isincreased, typically doubled. In some embodiments, and as alluded toabove, ACs are defined for classifying network traffic. Each AC(configured for access to/from an AP) is associated with a correspondingset of parameter values. The transmission of frames classified under aparticular AC can be transmitted according to the set of parametervalues corresponding to that particular AC. That is, ACs can be likenedto queues that an AP can populate with data, and from which that datacan be transmitted. Typically, there are four types of ACs (describedbelow) that can be assigned to different types of applications, eachhaving its own particular QoS requirements/parameters. Moreover, once anAC is assigned to an application type, the manner in which traffic/datais queued in an AC, along with the manner in which traffic/data is takenout of the queue can be configured. It should be understood that aparticular AC can be associated with one or more queues/sub-queues.

Table 2 below shows an example of four ACs (background (BK), best effort(BE), video (VI), and voice (VO)) and respective parameter values asconfigured for a first WLAN device.

TABLE 2 AC CWmin CWmax AIFS Max. TXOP Background 15 1023 7 0 (BK) BestEffort 15 1023 3 0 (BE) Video (VI) 7 15 2 3.008 ms Voice 3 7 2 1.5404ms  (VO)

In the above example, frames classified under the video category aretransmitted by the first WLAN device using value 7 for CWmin, value 15for CWmax, and value 2 for AIFS. A second WLAN device may be configureddifferently than the first WLAN device by using different parametervalues.

Table 3 below shows an example of four ACs and associated parametervalues as configured for a second WLAN device that is different than thefirst WLAN device.

TABLE 3 AC CWmin CWmax AIFS Max. TXOP Background 15 1023 7 0 (BK) BestEffort 15 1023 3 0 (BE) Video (VI) 5 10 1 3.008 ms Voice (VO) 3 7 21.5404 ms 

In the above example (see table 2 and table 3), frames classified underthe VI AC are transmitted by the second WLAN device using value 5 forCWmin, value 10 for CWmax, and value 1 for AIFS. The second WLAN devicecan be configured more aggressively than the first AP because the secondAP has lower values for CWmin, CWmax, and AIFS. This can result in, forthe second WLAN device, more frequent attempts to obtain channel accessand more frequent transmission of frames.

Thus, the first WLAN device and the second WLAN device compete foraccess to the shared channel (such as a radio frequency channel). In anexample, the first WLAN device attempts to transmit packets for aparticular video stream at the same time the second WLAN device istransmitting a first set of packets for another video stream. Since theradio frequency channel is unavailable to the first WLAN device (theradio frequency channel is being used by the second WLAN device to sendthe first set of packets), the first WLAN device again attempts totransmit after a random period of time that is computed based on CWminand/or CWmax (e.g. a period of time within 0 (or the SIFS time), and thelargest possible time based on CWmax. The random period of time may bereferred to herein as a random backoff time. However, the second WLANdevice may be transmitting a second set of packets when the first WLANdevice attempts again because the lower values for CWmin and CWmax usedby the second WLAN device result in the second WLAN device requestingchannel access more frequently than the first WLAN device. Furthermore,the second WLAN device transmits more frames per time period than thefirst WLAN device because the AIFS parameter value is lower for thesecond WLAN device. The difference in parameter values results in thesecond WLAN device using a channel, shared with the first WLAN device,for a larger percentage of time than the first WLAN device to transmitvideo data.

FIG. 2A is a schematic representation of an example AP 200 in accordancewith one embodiment. AP 200 may be a network device that can include,e.g., one or more of: a processor 202, memory/data storage 204, a radio206 (and corresponding antenna 206A), and prioritization logic 208.

Memory 204 may include a fast read-write memory for storing programs anddata during the AP 200's operations and a hierarchy of persistent memorysuch as ROM, EPROM, and Flash memory for storing instructions and dataneeded for the startup and/or operations of AP 200. Memory 204 may storedata that is to be transmitted from AP 200 or data that is received byAP 200. Memory 204 may store one or more of the various parameters (andvalues thereof) described herein. In some embodiments, memory 204 is adistributed set of data storage components. Although not shown, itshould be understood that AP 200 may further include input/outputinterfaces, including wired network interfaces such as IEEE 802.3Ethernet interfaces, as well as wireless network interfaces such as IEEE802.11 Wi-Fi interfaces, although examples of the disclosure are notlimited to such interfaces.

Processor 202 is coupled to at least memory 204. Processor 202 may beany processing device including, but not limited to a MIPS-classprocessor, a microprocessor, a digital signal processor, an applicationspecific integrated circuit, a microcontroller, a state machine, or anytype of programmable logic array.

Radio 206 may be a 5 GHZ radio, a 2.4 GHZ radio, a 6 GHz radio, or otherappropriate wireless communications component for effectuating wirelesscommunications. Radio 206 may be configured to both transmit and receivedata. Radio 206 may be dedicated to a communication channel 201. In someexamples, communication channel 201 operates on a communication band(e.g., 5.0 GHz UNII band) and operates in accordance with a particularwireless specification (e.g., 802.11ax). For example, by operating inaccordance with the particular specification such as IEEE 802.11ax,communication channel 201 can employ OFDMA, spatial reuse, MU-MIMO,and/or combinations thereof. By extension, a wireless client device/STAhaving a capacity of complying with the particular wirelessspecification can, in such examples, have the capacity for employingOFDMA, spatial reuse, UL MU-MIMO, and/or combinations thereof. It shouldbe understood that AP 200 may have a plurality of radios (physicaland/or logical), and may have dedicated or shared channels for eachradio or group(s) of radios.

In some embodiments, prioritization logic 208 may include one or morefunctional units implemented using firmware, hardware, software, or acombination thereof for configuring parameters associated with AP 200and/or client device/STA 210-1 for the transmission of data/frames toand from AP 200. Although, prioritization logic 208 is shown as beingimplemented on AP 200, one or more physical or functional components ofthe prioritization logic 208 may be implemented on a separate device,such as an AP controller, an example of which may be controller 104 ofFIG. 1A.

Various embodiments can prioritize those frames being sent in the ULand/or DL direction based on, for example, adjusting values for one ormore parameters as described herein, such as MU EDCA parameters and/orEDCA parameters. Various embodiments can dynamically prioritize thoseframe being sent from the client device/STA 210-1 and/or clientdevice/STA 210-2, for example, by dynamically adjusting one or moreparameters discussed herein (such as MU EDCA and/or EDCA parameters).

As illustrated in FIG. 2A, AP 200 may be receiving frames from STA210-1, STA-2, (and/or other client devices, not shown) overcommunications channel 201 in the UL direction, while transmittingframes to client device/STA 210-1, client device/STA 210-2 (and otherclient devices, not shown), in the DL direction. As will be discussed ingreater detail below with respect to FIG. 2B, one embodiment dynamicallyadjusts channel access priority (i.e. the values for of one or moreparameters (such as MU EDCA) to provide for increased access to the oneor more channels of the AP) by WLAN devices (e.g. AP 200, STA 210-1, STA210-2, or another WLAN device not shown). The logic for dynamicallyadjusting channel access priority (e.g. by adjusting one or moreparameters as described herein) can be included in prioritization logic208.

It should be understood that various embodiments are able to effectuatedynamic adjustment of channel access priority under a variety ofscenarios. For example, in some communication scenarios, there can benumerous client devices attempting to access the channel 201, (notshown), whereas in others, there can be a smaller number.

In some communication scenarios, for example, there can be mixed clients(i.e. employing a variety of channel access schemes and/or priorityschemes). For example, in some communication scenarios, a plurality ofclient devices can be accessing (or attempting to access) the channel201 by MU means, as compared to SU means. In some communicationscenarios, some number of client devices accessing (and/or attempting toaccess) the channel 201 can be non-MU capable client devices (and/orlegacy client devices). The same or another number of client devicesaccessing (and/or attempting to access) the channel 201 can be MU datacapable client devices. Of those MU data capable client devices, some orall may end up accessing the channel 201 by MU means, whereas others endup accessing the channel 201 by MU means.

For example, client device/STA 210-1 can be a MU data capable device,whereas client device/STA 210-2 can be a non-MU data capable device. Inthe UL, it may be preferable to prioritize channel access for the clientdevice/STA 210-1 (e.g. in the UL) as compared to client device/STA210-2. In the UL, it may be preferable to prioritize channel access forclient device/STA 210-1 over client device/STA 210-2, while stillminimizing (or otherwise tailoring) a risk of frame collisions forclient device/STA 210-1, 210-2, and any other WLAN device accessing thechannel 201.

It should be understood that the prioritized channel access as disclosedherein need not be limited for use with APs/AP controllers, but may beused to prioritize channel access between non-AP devices that, e.g.,operate in peer-to-peer or mesh network topologies. Hence, variousembodiments disclosed and/or contemplated herein can be used to enhancethe conventional channel access (i.e. wired and/or wireless), in two (ULand DL) directions relative to a given device (i.e. not necessarily aWLAN device). The dynamic prioritization of channel access can also beapplied or leveraged on a per-application basis. That is, if a network,e.g., network 100 (FIG. 1A) or some portion(s) thereof becomeoverloaded, certain applications may be afforded a higher priority thanothers.

As used herein, the term “traffic flow” can refer to a stream of datapackets, e.g., segments, frames, or datagrams, that share the samechannel. As used herein, the term “traffic flow” can refer to stream ofdata packets, e.g. segments, frames, or datagrams that same 5-tuple. Itshould be understood that the aforementioned 5-tuple can refer to a setof five different values that comprise a TCP/IP connection, andincludes: source IP address; a destination IP address; a source portaddress; a destination port address; and the protocol in use (TCP/UDP).

The manner in which data is characterized may be specified, e.g., by adeveloper or other entity, such that deep packet inspection (describedbelow) can be used to identify and classify this data traffic so that itcan be assigned to an appropriate AC, (or other EDCA or MU EDCAparameter) and ultimately, as disclosed herein, prioritized.

It should be noted that deep packet inspection can be performed ontraffic flows to determine whether the segments/datagrams for aparticular traffic should correspond to an advertised priority.Moreover, deep packet inspection can be performed as part of one or morenegotiation between the AP and client devices.

It can be understood that the prioritization of traffic, may depend oninternal software/hardware implementation aspects/characteristics thatcan impact or change the scheduling of traffic. That is, by analyzingthe metadata, AP implementations ensure that those traffic flows whichcorrespond to a high-priority (e.g. higher priority channel access) arescheduled and/or otherwise transmitted with a commensurately higherpriority over the air. This can be accomplished by adjusting one or moreparameters, such as MU EDCA or EDCA parameters. For example, this can beaccomplished by increasing the scheduling frequency for the trafficflows, and/or by ensuring that the AC in accordance with which datapackets in a traffic flow are transmitted (and in accordance with anyQoS requirement(s)).

FIG. 2B is a block diagram of an example computing component or device220 for prioritizing channel access in accordance with one embodiment.Computing component 220 may be, for example, a server computer, acontroller, or any other similar computing component capable ofprocessing data. In the example implementation of FIG. 2B, computingcomponent 220 includes a hardware processor, 222, and machine-readablestorage medium, 224. In some embodiments, computing component 220 may bean embodiment of a controller, e.g., a controller such as controller 104(FIG. 1A), or another component of wireless network 100, e.g., an APsuch as AP 106 a (FIG. 1A), for example.

Hardware processor 222 may be one or more central processing units(CPUs), semiconductor-based microprocessors, and/or other hardwaredevices suitable for retrieval and execution of instructions stored inmachine-readable storage medium, 224. Hardware processor 222 may fetch,decode, and execute instructions, such as instructions 226-238, tocontrol processes or operations for prioritizing one or more channelaccess (such as WLAN device or application). As an alternative or inaddition to retrieving and executing instructions, hardware processor222 may include one or more electronic circuits that include electroniccomponents for performing the functionality of one or more instructions,such as a field programmable gate array (FPGA), application specificintegrated circuit (ASIC), or other electronic circuits. Instructions226-238 can allow for dynamic and/or intelligent adjustment of channelaccess prioritization. Although instructions 226-238 are shown, it canbe understood that the instructions can be performed in any order,without some of the instructions shown, and/or with the inclusion ofother instructions not shown, and the instructions would still fallwithin the scope of the disclosure.

A machine-readable storage medium, such as machine-readable storagemedium 224, may be any electronic, magnetic, optical, or other physicalstorage device that contains or stores executable instructions. Thus,machine-readable storage medium 224 may be, for example, Random AccessMemory (RAM), non-volatile RAM (NVRAM), an Electrically ErasableProgrammable Read-Only Memory (EEPROM), a storage device, an opticaldisc, and the like. In some embodiments, machine-readable storage medium224 may be a non-transitory storage medium, where the term“non-transitory” does not encompass transitory propagating signals. Asdescribed in detail below, machine-readable storage medium 224 may beencoded with executable instructions, for example, instructions 226-238.

Hardware processor 222 may execute instruction 226 to identify WLANdevices in BSS, such as WLAN devices associated to AP and/or sensing thechannel. As discussed above, this can include determining which WLANdevices are sensing and/or accessing a channel, and/or which WLANdevices have received a beacon. Moreover, a more detailed identification(e.g. to determine one or more applications, can include examining oneor more header of a packet or frame, and/or deep packet inspection canbe performed on traffic flows.

Hardware processor 222 may execute instruction 228 to determine which ofthe WLAN devices (e.g. from those identified at execution of instruction226) are MU data capable and/or high efficiency client devices. This caninclude determining which WLAN devices are associated to the BSS and/orAP, that are MU data capable and/or high efficiency WLAN devices. Thiscan include determining which of the WLAN devices are 802.11ax awaredevices and/or not 802.11ax devices. This can include determining thehe-clients (e.g. the number of active high-efficiency clients that cansupport UL MU for data frames). This can include sending one or moretrigger frames associated with MU schemes, such as based on the 802.11axprotocol.

Hardware processor 222 may execute instruction 230 to determine which ofthe client devices (e.g. from those identified at execution ofinstruction 226) are active client devices. Instruction 230 can includedetermining which of the WLAN devices are active WLAN devices.Instruction 230 can include determining which of the WLAN devices are orhave indicated (e.g. to the AP) that they are in power save mode (ornot). If a device is in power save mode, the device can be consideredinactive (or not). Instruction 230 can include examining one or more DLand/or UL queue to determine which devices have frames and/or traffic inthe queue to be transmitted. Instruction 230 can include examining thenumber of WLAN devices and/or which WLAN devices have data buffered atthe WLAN device for transmission. Instruction 230 can includedetermining which (and how many) WLAN devices are sensing thetransmission channel. Executing instructions 228 and/or 230 can includesorting the client devices (i.e. the client devices that were identifiedat step 226), e.g. by a requested priority, and/or the amount of databuffered. Executing instructions 228 and/or 230 can include determiningwhich WLAN devices are not MU capable devices.

As described herein, one or more parameters can be dynamically adjusted,e.g. based on the number of active MU capable client devices, thehe-clients, and/or the total number of active client devices in the BSS,such as a ratio thereof (he-client-density). The parameters can beadjusted based on the numerosity and/or the mix of client devices in theBSS (or associated to the AP).

Thus, hardware processor 222 can include instruction 232 for determiningthe he-client-density. He-client-density can be determined based on thetotal number of active client devices associated to the AP (and/or inthe BSS) and the number of active high-efficiency client devices.He-client-density can be determined based on the total number of activeclient devices associated to the AP (and/or in the BSS) and the numberof active MU capable client devices. He-client-density can be determinedbased on the total number of active client devices associated to the AP(and/or in the BSS) and the number of MU capable client devices.He-client-density can be determined based on the total number of clientdevices associated to the AP (and/or in the BSS) and the number of MUcapable client devices. He-client-density can be determined by one ormore determinations as described herein, including, for example, bycalculating a ratio and/or making a comparison. For example, determininghe-client-density can include calculating a ratio of the number ofactive MU capable client devices and the total number of active clientdevices in the BSS (and/or associated to the AP). As another example,he-client-density can be determined by comparing the total number of(active) client devices associated to the AP (or part of the BSS) to thenumber of active high-efficiency client devices, to the number ofhigh-efficiency client devices, to the number of MU data capabledevices, to the number of (active) MU data capable WLAN devices, to thenumber of (active) legacy (i.e. non 802.11ax) devices, and/or to thenumber of (active) MU data capable device which disable MU for dataframes (e.g. in the UL) (or any combination, such as a summation,thereof).

Hardware processor 222 can include instruction 234 for comparinghe-client-density to a density threshold. The threshold can be apercentage and/or number between 0 and 1. For example, the threshold canbe 50%, 49%, 45%, 40%, 35%, 30%, 25%, 10%, 05%, 01%. In embodiments, thethreshold can dynamically adjust depending on one or more informationobtained when executing instructions 226-232, e.g. depending on thenumber of active high-efficiency client devices and/or the number ofactive client devices. The threshold can adjust dynamically depending onvalues for one or more parameters, such as values for EDCA parametersand/or MU EDCA parameters. For example, the threshold can depend on thevalue for AC. As another example, the threshold can adjust depending onthe number or prior unsuccessful transmission attempts.

It is understood that one or more instructions 232 and 234 can includedetermining any ratio between and/or otherwise comparing at least twoof:the total number of (active) client devices associated to the AP orpart of the BSS, the number of (active) high efficiency client devices,the total number of active client devices associated to the AP less thenumber of active high-efficiency client devices (i.e. the rest of theclient devices). For clarity, this is reflected in FIG. 2C.

Hardware processor 222 can include instruction 236 for dynamicallyadjusting one or more parameters, such as MU EDCA parameters and/or EDCAparameters, if the he-client-density is less than and/or equal to thethreshold (i.e. is not greater than and/or equal to the threshold).Instruction 236 can include adjusting the one or more parameters whenthe total number of active client devices associated to the AP less thenumber of active high-efficiency client devices, exceeds the number ofactive high-efficiency client devices. Instruction 236 can includeadjusting the one or more parameters, when the number of activehigh-efficiency client devices is less than the total number of activeclient devices associated to the AP less the number of activehigh-efficiency client devices. Instruction 236 can include adjustingone or more parameters so access to one or more channels of the AP isincreased by the high-efficiency client devices (e.g. those determinedat execution of instruction 228). Instruction 236 can include adjustingone or more parameters so MU EDCA parameters are set to be moreaggressive than EDCA parameters. Instruction 236 can include adjusting avalue of the parameter based on the number of active high efficiencyclient devices, and/or the number of total active client devices. Thisinstruction can include one or more prioritization logic as describedherein. Other means of dynamically adjusting one or more parameter, e.g.for dynamic adjustment of channel access prioritization, have beendescribed herein. It is understood that execution of instruction 236 caninclude these other means of dynamically adjusting one or moreparameters discussed herein.

Hardware processor 222 can include instruction 238 for dynamicallyadjusting one or more parameters, such as MU EDCA parameters and/or EDCAparameters, if the he-client-density is greater than and/or equal to thethreshold. Instruction 238 can include adjusting the one or moreparameters, when the number of active high-efficiency client devicesexceeds the total number of active client devices associated to the APless the number of active high-efficiency STA. Instruction 238 canincluding adjusting the one or more parameters, when the total number ofactive client devices associated to the AP less the number of activehigh-efficiency STA, is less than the number of active high efficiencyclient devices. Instruction 238 can include dynamically adjusting oradapting a MU EDCA parameter set (e.g. adjusting one or more valuesthereof) to provide for decreased access to one or more channels of theAP by the high-efficiency client devices. Instruction 238 can includedynamically adjusting or adapting a MU EDCA parameter set (e.g.adjusting one or more values thereof) to provide for decreased access toone or more channels of the AP by the high-efficiency client devices,but not less than the access to the one or more channels afforded to thenon-high-efficiency client devices.

Instruction 238 can include dynamically adapting the MU EDCA parameterset to equal the EDCA parameter set so as to reduce collisions betweenthe high-efficiency client devices. Instruction 238 can includeadjusting one or more parameters so that MU EDCA parameters are set tobe as aggressive (or conservative) as EDCA parameters. Instruction 238can include adjusting one or more parameters so MU EDCA parameters areset to be less aggressive (or more conservative) than EDCA parameters.Legacy EDCA parameters can be made more conservative so that if MU EDCAparameters are set to the original value of legacy EDCA parameters, theMU EDCA parameters can still remain more aggressive than the new legacyEDCA parameters. Instruction 238 can include adjusting a value of atleast one parameter based on the number of active high efficiency clientdevices, and/or the number of total active client devices. Thisinstruction can include one or more prioritization logic as describedherein. This instruction can allow for dynamic adjustment of channelaccess prioritization, examples of which have been described herein.This instruction can dynamically adjust one or more parameters, such asMU EDCA parameters for channel access prioritization, examples of whichhave been described herein. It is understood that execution ofinstruction 238 can include means of dynamically adjusting one or moreparameters discussed herein.

One or more of the instructions 226-238 can be repeated, so that one ormore parameters as described herein are dynamically adjusted based onrequirements (such as channel access priority requirements, but alsocollision avoidance requirements) for the BSS and/or individual clientdevices. One or more of the instructions 226-238 can be repeated so thatone or more parameters are adjusted (e.g. at execution of instructions236 and/or 238) based on a comparison of he-client-density to more thanone thresholds (e.g. by adjusting the threshold each subsequentexecution of instruction 234). One or more of the instructions 226-238can be repeated so that one or more parameters are adjusted based on thevariety of client devices (and numbers and/or proportions thereof)associated to the AP (or part of the BSS). It is understood that one ormore of the instructions 234-238 can be performed simultaneously.

FIG. 2C depicts another block diagram of an embodiment of examplecomputing component or device 220 for prioritizing channel access. Inthe example implementation of FIG. 2C, similar to the exampleimplementation of FIG. 2B, computing component 220 includes a hardwareprocessor, 222, and machine-readable storage medium, 224. In someembodiments, computing component 220 may be an embodiment of acontroller, e.g., a controller such as controller 104 (FIG. 1A), oranother component of wireless network 100, e.g., an AP such as AP 106 a(FIG. 1A), for example.

Hardware processor 222 may fetch, decode, and execute instructions, suchas instructions 226-256, to control processes or operations forprioritizing one or more channel access (such as WLAN device orapplication). As an alternative or in addition to retrieving andexecuting instructions, hardware processor 222 may include one or moreelectronic circuits that include electronic components for performingthe functionality of one or more instructions, such as a fieldprogrammable gate array (FPGA), application specific integrated circuit(ASIC), or other electronic circuits. Instructions 226-256 can allow fordynamic and/or intelligent adjustment of channel access prioritization.Although instructions 226-256 are shown, it can be understood that theinstructions can be performed in any order, without some of theinstructions shown, and/or with the inclusion of other instructions notshown, and the instructions would still fall within the scope of thedisclosure.

As described in detail below, machine-readable storage medium 224 may beencoded with executable instructions, for example, instructions 226-256.

Hardware processor 222 may execute instructions 226-230, which can bethe same or similar instructions as instructions 226-230 shown in FIG.2B. Hardware processor 22 may execute instruction 226 to identify WLANdevices in BSS, such as WLAN devices associated to AP and/or sensing thechannel. Hardware processor 222 may execute instruction 228 to determinewhich of the WLAN devices are MU data capable and/or high efficiencyclient devices. This can include determining which WLAN devices areassociated to the BSS and/or AP, that are MU data capable and/or highefficiency WLAN devices. This can include determining which of the WLANdevices are 802.11ax aware devices and/or not 802.11ax devices. This caninclude determining the HE-clients.

Hardware processor 222 may execute instruction 230 to determine which ofthe client devices (e.g. those identified at execution of instruction226) are active client devices. Instruction 230 can include determiningwhich of the WLAN devices are active WLAN devices. Instruction 230 caninclude examining one or more DL and/or UL queue to determine whichdevices have frames and/or traffic in the queue to be transmitted.Instruction 230 can include examining the number of WLAN devices and/orwhich WLAN devices have data buffered at the WLAN device fortransmission. Instruction 230 can include determining which (and howmany) WLAN devices are sensing the transmission channel. Executinginstructions 228 and/or 230 can include sorting the client devices (i.e.the client devices that were identified at step 226), e.g. by arequested priority, and/or the amount of data buffered. Executinginstructions 228 and/or 230 can include determining which WLAN devicesare not MU capable devices or not high efficiency client devices.

As described herein, one or more parameters can be dynamically adjusted.For example, the one or more parameters can be adjusted based on thenumber of active MU capable client devices, the number of thehe-clients, and/or the total number of active client devices in the BSS(for example, based on a comparison and/or a ratio thereof). In general,the parameters can be adjusted based on the numerosity and/or the mix ofclient devices in the BSS (or associated to the AP).

Thus, hardware processor 222 can include instruction 252 for making acomparison of the number of (active) HE-clients, to the number of(total) (active) clients less the number of (active) HE-clients.Instruction 252 can include a comparison of the number of HE-clients toa number of other client devices associated to the AP and/or in the BS.The number of devices compared can be one or more client devices asdetermined at execution of either or all of instructions 226-230.

The number of he-clients can be total number of (active) client devicesassociated to the AP (and/or in the BSS) which are MU capable clientdevices.

Hardware processor 222 can include instructions 254-256 for dynamicallyadjusting one or more parameters, such as MU EDCA parameters and/or EDCAparameters, depending on an outcome of execution of instruction 252.

Hardware processor 222 can execute instruction 254 when the total numberof (active) client devices associated to the AP less the number of(active) high-efficiency client devices, exceeds (or is equal to) thenumber of (active) high-efficiency client devices. Instruction 254 canbe the same or similar to instruction 236 described with reference toFIG. 2B. Hardware processor 222 can execute instruction 254 when thenumber of (active) high-efficiency client devices does not exceed thetotal number of (active) client devices associated to the AP less thenumber of (active) high-efficiency client devices.

Execution of instruction 254 can include adjusting the one or moreparameters. Instruction 236 can include adjusting one or more parametersso access to one or more channels of the AP is increased by thehigh-efficiency client devices (e.g. those determined at execution ofinstruction 228). Instruction 254 can include adjusting one or moreparameters so MU EDCA parameters are set to be more aggressive than EDCAparameters. Instruction 254 can include adjusting a value of at leastone parameter in a parameter set based on the number of (active) highefficiency client devices, and/or the number of total (active) clientdevices. This instruction can include one or more prioritization logicas described herein. Other means of dynamically adjusting one or moreparameter, e.g. for dynamic adjustment of channel access prioritization,have been described herein. It is understood that execution ofinstruction 254 can include these other means of dynamically adjustingone or more parameters discussed herein.

Hardware processor 222 can include instruction 256 for dynamicallyadjusting one or more parameters, such as MU EDCA parameters and/or EDCAparameters, when the number of (active) high-efficiency client devicesexceeds (or is equal to) the total number of (active) client devicesassociated to the AP (or part of the BSS) less the number of (active)high-efficiency client devices. Instruction 256 can be the same orsimilar to instruction 238 as described with reference to FIG. 2B.Instruction 256 can including adjusting the one or more parameters, whenthe total number of (active) client devices associated to the AP (orpart of the BSS) less the number of (active) high-efficiency clientdevices, is less than (or equal to) the number of active high efficiencyclient devices. Instruction 256 can include dynamically adjusting oradapting a MU EDCA parameter set (e.g. adjusting one or more valuesthereof) to provide for decreased access to one or more channels of theAP by the high-efficiency client devices. Instruction 256 can includedynamically adjusting or adapting a MU EDCA parameter set (e.g.adjusting one or more values thereof) to provide for decreased access toone or more channels of the AP by the high-efficiency client devices,but not less than access afforded to non-high efficiency client devices.

Instruction 256 can include dynamically adapting the MU EDCA parameterset to equal the EDCA parameter set so as to reduce collisions betweenthe high-efficiency client devices. Instruction 256 can includeadjusting one or more parameters so that MU EDCA parameters are set tobe as aggressive (or conservative) as EDCA parameters. Instruction 256can include adjusting one or more parameters so MU EDCA parameters areset to be less aggressive (or more conservative) than EDCA parameters.Legacy EDCA parameters can be made more conservative so that if MU EDCAparameters are set to the original value of legacy EDCA parameters, theMU EDCA parameters can still remain more aggressive than the new legacyEDCA parameters. Instruction 256 can include adjusting a value of atleast one parameter based on the number of active high efficiency clientdevices, and/or the number of total active client devices. For example,instruction 256 can include adjusting a value of at least one parameter,if the number of active high efficiency client devices, and/or thenumber of total active client devices is below and/or above a thresholdvalue. This instruction can include one or more prioritization logic asdescribed herein. This instruction can allow for dynamic adjustment ofchannel access prioritization, examples of which have been describedherein. This instruction can dynamically adjustment one or moreparameters, such as MU EDCA parameters for channel accessprioritization, examples of which have been described herein. It isunderstood that execution of instruction 256 can include these othermeans of dynamically adjusting one or more parameters discussed herein.

One or more of the instructions 226-256 can be repeated, so that one ormore parameters as described herein are dynamically adjusted based onrequirements (such as channel access priority requirements, but alsocollision avoidance requirements) for the BSS and/or individual clientdevices. One or more of the instructions 226-256 can be repeated so thatone or more parameters are adjusted (e.g. at execution of instructions254 and/or 256) based on the variety of client devices (and numbers orproportions thereof) associated to the AP (or part of the BSS). It isunderstood that one or more of the instructions 252-256 can be performedsimultaneously. For example, if MU EDCA parameters are set moreaggressive at execution of instruction 236, then the level ofaggressiveness can be determined by knowing the absolute number ofhe-clients or MU UL data capable clients, (i.e. as part of execution ofinstruction 252) and the level of aggressiveness can be adapted to atexecution of instruction 254 (i.e. by dynamic adjustment of MU EDCAparameters).

Hardware processor 222 shown in FIG. 2B and/or FIG. 2C can furtherinclude instructions for sorting, scheduling, and/or allocatingresources for one or more of the client devices (not shown, but can beincluded in instructions 226-256, or before or after either of theseinstructions). For example, client devices can be sorted based on thepriority for channel access, e.g. based on application type, AC, datasize in buffer. Hardware processor 222 shown in FIG. 2B and/or FIG. 2Ccan further include one or more instructions for sending one or moretrigger frames and/or scheduling instructions as described herein (notshown, but can be included in instructions 226-256, and/or before orafter either of these instructions).

The client devices with higher priority can be scheduled for ULtransmissions more often than the other client devices, at least bymaking one or more parameters more aggressive. Such client devices canalso be provided more channel resources for their transmissions. Thisincrease in channel resources can translate to larger resource units(RUs) in the case of scheduled UL OFDMA, or a greater number of spatialstreams in the case of scheduled UL MU-MIMO. This increase in channelresources can translate to more aggressive EDCA parameters and/or MUEDCA parameters in the case of SU (such as CSMA/CA) (e.g. as adjustedwhen executing instructions 226-238). Hardware processor 222 shown inFIG. 2B and/or FIG. 2C can determine the AC (or other QoS parameter) ofcorresponding transmissions. The AP can then use trigger frame (or otherscheduling information) to schedule the client device to transmit framesusing MU (e.g. OFDMA, MU-MIMO, or a combination thereof), and/or SU(i.e. by CSMA/CA with EDCA and/or MU EDCA parameters). In someembodiments, the trigger frame may include values for one or moreparameters, such as EDCA and/or MU EDCA parameters, including but notlimited to AC, CWmin, CWmax, and/or MU EDCA timer. In some embodiments,a beacon (e.g. by the AP) may include values for one or more parameters,such as EDCA and/or MU EDCA parameters, including but not limited to AC,CWmin, CWmax, and/or MU EDCA timer. The beacon can be a managementframe. In some embodiments, a probe response may include the values forone or more parameters, such as EDCA and/or MU EDCA parameters,including but not limited to AC, CWmin, CWmax, and/or MU EDCA timer.

For example, in some embodiments, EDCA parameter set can be sent with abeacon (e.g. before executing instruction 234), and a trigger frameincluding one or more updated parameters (e.g. parameters adjustedand/or updated at execution of instructions 236 and/or 238) can be sentat or after execution of either of instructions 234-348. The sequence ofbeacons and trigger frames is generally reflected in FIG. 2D.

It should be understood that trigger frames can be used to relayinformation (from an AP) regarding the time when a client device canbegin transmitting its queued data/packets/frames to the AP, along withinformation regarding transmit rate, transmit power, RU size, andspatial streams/subchannels allocated to the receiving client device(discussed above). With the use of such trigger frame information, inconjunction with other fields and/or information, a client device can bemade and/or instructed to transmit its queued frames according to thedesired priority (discussed in greater detail below). It is understoodthat trigger frames can be adjusted so that priority is optimized forthe STA, but also in view of the totality of client devices in the BSS.For example, the RU size can be optimized for UL transmission. It isunderstood that trigger frames can be tailored for one or more desiredand/or determined transmission mode for each WLAN device. It isunderstood that trigger frames can be tailored for the DL and/or ULdirection.

Sorted client devices having the highest priority can be the ones forwhich RU size is maximized. The Resource Unit (RU) assignment to otherclient devices can be prioritized against other client devices, both interms of how often they are assigned the RUs)(selected for OFDMAtransmissions) as well as the size of the RUs. In some embodiments, theRU size assigned to client devices with the smaller UL queue-depth willbe proportional to airtime determined by the number of bytes queued inthe STA. For client devices with larger UL queue-depth(s), the entirechannel width can be allocated for the RU. It should be understood thatUL queue-depth can be implementation-dependent, and thus, in someembodiments, an applicable queue-depth threshold can be specifiedagainst which STA queue-depth can be compared to determine if thequeue-depth is “smaller” than the threshold or “larger” than thethreshold.

Sorted client devices having the highest priority can be those for whichone or more parameters are set more aggressive (e.g. SU relatedparameters). Higher priority client devices can be prioritized againstother client devices, by adjusting one or more of the EDCA and/or MUEDCA parameters, including but not limited to AC, CWmin, CWmax, and/orMU EDCA timer, to be more aggressive.

Hardware processor 222 of FIG. 2B and/or FIG. 2C may execute instruction(not shown) to determine the UL transmission mode for each clientdevice. In some embodiments, UL MU-MIMO can be used for datatransmission within RUs for client devices with high priority fortransmitting frames from those client devices to the AP. client deviceswith smaller UL queue-depth (measured in bytes) may be configured to useUL MU OFDMA. For clients with a limited number of antennas, again,partial bandwidth UL MU-MIMO can be used within the RU, effectivelysharing it between the high-priority client devices, while ensuring thelatency among the high-priority client devices is minimized. For clientdevices with larger UL queue-depth, which as noted above, can beallocated an entire channel-width for the RU, full bandwidth UL MU-MIMOcan still be used across client devices. It should be noted that even inthis case, such client devices are prioritized in terms of the number oftimes they are grouped for MU-MIMO transmissions and the number ofspatial streams assigned to them.

In accordance with some embodiments, the prioritization of channelaccess and traffic can be performed in conjunction with an AP upgrade.Accordingly, hardware processor 222 shown in FIG. 2B and/or FIG. 2C mayexecute one or more instruction (not shown) to perform DL and/or ULscheduling. It should be understood that channel access prioritizationdescribed above can be performed or used independently, or in additionto/conjunction with any other form of prioritization used for UL and/orDL traffic, where some “net” prioritization can be achieved usingmultiple mechanisms (i.e., that described herein and anotherprioritization mechanism(s)).

FIG. 2D shows an example method and general timing diagram 259 foreffectuating dynamically prioritized channel access in a BSS inaccordance with some embodiments. As shown in FIG. 2D and as describedherein, channel access can be dynamically prioritized by dynamicadjustment of values for one or more parameters for communication overthe channel.

One or more portions of the method can be executed by WLAN devices (e.g.processors thereof). A BSS can include AP 260. AP 260 can be AP 201 asshown in FIG. 2A, and/or include hardware processor 222 as shown in FIG.2B and/or FIG. 2C. The BSS can include one or more client devices. Theseclient devices can include client devices 210-1 and/or 210-2 as shownwith reference to FIG. 2A. The BSS can include one or more highefficiency or MU-data capable client devices, shown here as HE clientdevices 262-1 to 262-N. The BSS can further include one or more legacy,non-high efficiency client devices, or non-MU data capable devices,shown here as non he-client device 264.

The AP 260 can perform step 266 for sending a beacon with one or moreparameters, such as legacy EDCA parameters. The one or more clientdevices can perform step 268 for updating a set of parameters (such aslegacy EDCA parameters) based on the beacon.

The AP 260 can perform step 270 for determining the BSS composition andupdate values for one or more parameters. The values for the one or moreparameters can be updated based on the BSS composition (among otherreasons). The values for the one or more parameters can be updated sothat channel access priority is dynamically configured. Performing step270 can include determining the variety of client devices (and numbersand/or proportions thereof) associated to the AP (or part of the BSS).Performing step 270 can include determining number of active MU capableclient devices or high efficiency clients, and/or the total number ofactive client devices in the BSS or associated to AP 260. Performingstep 270 can include determining values for one or more parameters basedon the variety of client devices (and numbers and/or proportionsthereof) associated to the AP (or part of the BSS). The values for oneor more parameters can be such, that channel access is prioritized forMU-capable or high efficiency client devices (such as 802.11ax clientdevices) over non-MU-capable or non HE-client devices, even if theMU-capable or high efficiency client devices choose to employ SU meansof channel access. However, the values for one or more parameters canalso be such that the risk for one or more frame collisions isconsidered (e.g. minimized).

Performing step 270 can include execution of one or more of instructions226-256 as described with reference to FIG. 2B and/or FIG. 2C. It can beunderstood that steps 266 and/or 268 can be performed at or around thesame time, or interchangeably with step 270.

AP 260 can perform step 272 for sending a trigger with one or moreupdated (e.g. adjusted or not adjusted) parameters. The updatedparameters can be the parameters as updated at step 270. The trigger canbe part of a trigger frame or other frame that can include one or morescheduling information for devices. For example, the trigger frame basedbe based on a determined transmission mode for each client device. Thetrigger can be sent to specific HE-devices. For example, trigger at step272 can be sent to high efficiency client device 262-1. When received byhigh efficiency client device 262-1, the client device can perform step274 for updating the parameters (i.e. values thereof). The HE-clientdevice 262-1 can then transmit one or more frames based on theinformation from the trigger, and based on the updated parameters. Forexample, the HE client device can transmit one or more frames accordingto SU and/or MU schemes as described herein (steps not shown in FIG.2D).

In some embodiments a trigger may be unique for each device, and/orvalues of parameters can be unique to each device. As such, in someembodiments, the AP 260 can perform step 276 and step 278 foriteratively sending one or more triggers with updated parameters to theone or more other client devices. For example, step 278 can includesending a trigger with updated parameters (such as legacy EDCA and/or MUEDCA parameters) to client device 262-N. For example, trigger sent toclient device 262-N (e.g. at steps 276-278) can include updated valuesfor MU EDCA parameters such as CWmin, CWmax, and MU EDCA timer. Clientdevice 262-N can perform step 280 of updating values for the parametersbased on the trigger. For example, the updated parameters can havevalues which were different compared to values of the parameters atexecution of step 268. Client device 262-N can transmit one or moreframes based on those updated parameters, e.g. by SU and/or MU means(step not shown in FIG. 2D).

It is understood that the various WLAN devices part of a BSSconfiguration and/or associated to the AP 260 can receive the one ormore parameters as determined by methods and systems described herein,and can additionally transit frames based on values for thoseparameters.

FIG. 3 depicts a block diagram of an example computer system 300 inwhich various of the embodiments described herein may be implemented.The computer system 300 includes a bus 302 or other communicationmechanism for communicating information, one or more hardware processors304 coupled with bus 302 for processing information. Hardwareprocessor(s) 304 may be, for example, one or more general purposemicroprocessors.

The computer system 300 also includes a main memory 306, such as arandom access memory (RAM), cache and/or other dynamic storage devices,coupled to bus 302 for storing information and instructions to beexecuted by processor 304. Main memory 306 also may be used for storingtemporary variables or other intermediate information during executionof instructions to be executed by processor 304. Such instructions, whenstored in storage media accessible to processor 304, render computersystem 300 into a special-purpose machine that is customized to performthe operations specified in the instructions.

The computer system 300 further includes a read only memory (ROM) 308 orother static storage device coupled to bus 302 for storing staticinformation and instructions for processor 304. A storage device 310,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 302 for storing information andinstructions.

Computer system 300 may further include at least one network interface312, such as a network interface controller (NIC), network adapter, orthe like, or a combination thereof, coupled to bus 302 for connectingcomputer system 300 to at least one network.

In general, the word “component,” “system,” “database,” and the like, asused herein, can refer to logic embodied in hardware or firmware, or toa collection of software instructions, possibly having entry and exitpoints, written in a programming language, such as, for example, Java, Cor C++. A software component may be compiled and linked into anexecutable program, installed in a dynamic link library, or may bewritten in an interpreted programming language such as, for example,BASIC, Perl, or Python. It will be appreciated that software componentsmay be callable from other components or from themselves, and/or may beinvoked in response to detected events or interrupts. Softwarecomponents configured for execution on computing devices may be providedon a computer readable medium, such as a compact disc, digital videodisc, flash drive, magnetic disc, or any other tangible medium, or as adigital download (and may be originally stored in a compressed orinstallable format that requires installation, decompression ordecryption prior to execution). Such software code may be stored,partially or fully, on a memory device of the executing computingdevice, for execution by the computing device. Software instructions maybe embedded in firmware, such as an EPROM. It will be furtherappreciated that hardware components may be comprised of connected logicunits, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors.

The computer system 300 may implement the techniques described hereinusing customized hard-wired logic, one or more ASICs or FPGAs, firmwareand/or program logic which in combination with the computer systemcauses or programs computer system 300 to be a special-purpose machine.According to one embodiment, the techniques herein are performed bycomputer system 300 in response to processor(s) 304 executing one ormore sequences of one or more instructions contained in main memory 306.Such instructions may be read into main memory 306 from another storagemedium, such as storage device 310. Execution of the sequences ofinstructions contained in main memory 306 causes processor(s) 304 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device310. Volatile media includes dynamic memory, such as main memory 306.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between non-transitory media. For example, transmissionmedia includes coaxial cables, copper wire and fiber optics, includingthe wires that comprise bus 302. Transmission media can also take theform of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, the description of resources, operations, orstructures in the singular shall not be read to exclude the plural.Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing, the term “including” shouldbe read as meaning “including, without limitation” or the like. The term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof. The terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike. The presence of broadening words and phrases such as “one ormore,” “at least,” “but not limited to” or other like phrases in someinstances shall not be read to mean that the narrower case is intendedor required in instances where such broadening phrases may be absent.

What is claimed is:
 1. A method for prioritizing access point (AP)channel access, comprising: determining a number of active uplink (UL)multi-user (MU) data capable stations (STAs) associated to the AP;determining a total number of active STAs associated to the AP;dynamically adapting a MU enhanced distributed channel access (EDCA)parameter set to provide for increased access to one or more channels ofthe AP by the UL MU data capable STAs when the total number of activeSTAs associated to the AP less the number of active UL MU data capableSTAs exceeds the number of active UL MU data capable STAs; anddynamically adapting the MU EDCA parameter set to equal a legacy EDCAparameter set to reduce collisions between the UL MU data capable STAswhen the number of active UL MU data capable STAs exceeds or equals thetotal number of active STAs associated to the AP less the number ofactive UL MU data capable STAs.
 2. The method of claim 1, furthercomprising determining that the number of active UL MU data capable STAsexceeds the total number of active STAs associated to the AP less thenumber of active UL MU data capable STAs, by determining that a densityof active UL MU data capable STAs compared to the total number of activeSTAs associated to the AP exceeds or is equal to a first densitythreshold value.
 3. The method of claim 2, further comprisingdetermining that the total number of active STAs associated to the APless the number of active UL MU data capable STAs exceeds the number ofactive UL MU data capable STAs, by determining the density of active ULMU data capable STAs compared to the total number of active STAsassociated to the AP, does not exceed the first density threshold value.4. The method of claim 3, further comprising dynamically adapting the MUEDCA parameter set to provide for even more increased access to the oneor more channels of the AP by the UL MU data capable STAs when thedensity of active UL MU data capable STAs compared to the total numberof active STAs associated to the AP does not exceed a second densitythreshold value, wherein the second density threshold value is lowerthan the first density threshold value.
 5. The method of claim 3,further comprising dynamically adapting the MU EDCA parameter set toprovide for even more increased access to the one or more channels ofthe AP by the UL MU data capable STAs when the total number of activeSTAs associated to the AP is less than a Basic Service Set (BSS) STApopulation size threshold value.
 6. The method of claim 5, whereindynamically adapting the MU EDCA parameter set to provide for even moreincreased access to one or more channels of the AP comprises adjustingone or more of the MU EDCA parameters to be even more aggressive.
 7. Themethod of claim 1, wherein dynamically adapting the MU EDCA parameterset comprises adjusting at least one of a minimum contention window(CWmin), a maximum contention window (CWmax), or a MU EDCA timer.
 8. Themethod of claim 7, further comprising adjusting the CWmin parameter whenthe total number of active STAs associated to the AP less the number ofactive UL MU data capable STAs exceeds the number of active UL MU datacapable STAs, and wherein a value to which CWmin is adjusted depends onthe number of active UL MU data capable STAs.
 9. The method of claim 7,further comprising adjusting the CWmin parameter when the total numberof active STAs associated to the AP less the number of active UL MU datacapable STAs exceeds the number of active UL MU data capable STAs, andwherein the value to which CWmin is adjusted is half or less than halfof a value for a legacy CWmin parameter of the legacy EDCA parameterset.
 10. The method of claim 7, further comprising adjusting the CWminparameter when the total number of active STAs associated to the AP lessthe number of active UL MU data capable STAs exceeds the number ofactive UL MU data capable STAs, and wherein a value to which CWmin isadjusted is set to be more aggressive than a value of a legacy CWminparameter of the legacy EDCA parameter set.
 11. The method of claim 7,further comprising adjusting the MU EDCA timer, wherein the value forthe MU EDCA timer is determined based on an amount of data buffered atthe active-UL MU data capable STAs and the number of UL MU data capableSTAs, such that each of the UL MU data capable STAs can be scheduled atleast once before an expiration of the MU EDCA timer.
 12. An accesspoint (AP) configured to prioritize access to one or more channels ofthe AP, comprising: a hardware processor; a machine readable storagemedium comprising one or more instructions, wherein when theinstructions are executed by the hardware processor, the AP: determinesa number of active uplink (UL) multi-user (MU) data capable stations(STAs) associated to the AP; determines a total number of active STAsassociated to the AP; dynamically adapts a MU enhanced distributedchannel access (EDCA) parameter set to provide for increased access tothe one or more channels of the AP by the UL MU data capable STAs whenthe total number of active STAs associated to the AP less the number ofactive UL MU data capable STAs exceeds the number of active UL MU datacapable STAs; dynamically adapts the MU EDCA parameter set to equal alegacy EDCA parameter set to reduce collisions between the UL MU datacapable STAs when the number of active UL MU data capable STAs exceedsthe total number of active STAs associated to the AP less the number ofactive UL MU data capable STAs.
 13. The AP of claim 12, wherein the oneor more instructions are configured such that when executed by thehardware processor, the AP further determines that the number of activeUL MU data capable STAs exceeds the total number of active STAsassociated to the AP less the number of active UL MU data capable STAs,by determining that a density of active UL MU data capable STAs comparedto the total number of active STAs associated to the AP exceeds or isequal to a first density threshold value.
 14. The AP of claim 12,wherein the one or more instructions are configured such that whenexecuted by the hardware processor, the AP further determines that thenumber of active uplink (UL) MU data capable STAs exceeds the totalnumber of active STAs associated to the AP less the number of active ULMU data capable STAs, by determining a density of active UL MU datacapable STAs compared to the total number of active STAs associated tothe AP, does not exceed a first density threshold value.
 15. The AP ofclaim 14, wherein the one or more instructions are configured such thatwhen executed by the hardware processor, the AP dynamically adapts theMU EDCA parameter set to provide for even more increased access to theone or more channels of the AP by the UL MU data capable STAs, when thedensity of active UL MU data capable STAs compared to the total numberof active STAs associated to the AP does not exceed a second densitythreshold value, wherein the second density threshold value is lowerthan the first density threshold value.
 16. The AP of claim 14, whereinthe one or more instructions are configured such that when executed bythe hardware processor, the AP dynamically adapts the MU EDCA parameterset to provide for even more increased access to the one or morechannels of the AP by the UL MU data capable STAs when the total numberof active UL MU data capable STAs associated to the AP is less than a ULMU data capable STA population size threshold value.
 17. The AP of claim12, wherein the one or more instructions are configured such that whenexecuted by the hardware processor, the AP dynamically adapts the MUEDCA parameter set to provide for even more increased access to one ormore channels of the AP by adjusting one or more of the MU EDCAparameters to be more aggressive.
 18. The AP of claim 12, wherein theone or more instructions are configured such that when executed by thehardware processor, the AP dynamically adapts the MU EDCA parameter setby adjusting at least one of a minimum contention window (CWmin), amaximum contention window (CWmax), or a MU EDCA timer.
 19. The AP ofclaim 18, wherein the one or more instructions are configured such thatwhen executed by the hardware processor, the AP adjusts the CWminparameter when the total number of active STAs associated to the AP lessthe number of active UL MU data capable STAs exceeds the number ofactive UL MU data capable STAs, and wherein a value to which CWmin isadjusted is half or less than half of a value for a legacy CWminparameter of the legacy EDCA parameter set.
 20. The method of claim 18,further comprising adjusting the MU EDCA timer, wherein the value forthe MU EDCA timer is determined based on an amount of data buffered atthe active UL MU data capable STAs and the number of UL MU data capableSTAs, such that each of the UL MU data capable STAs can be scheduledonce before an expiration of the MU EDCA timer.